Skip to content

chore: Update governance rules by removing CODEOWNERS reference#30

Merged
damaz91 merged 1 commit into
mainfrom
chore/remove-codeowners
Jun 24, 2026
Merged

chore: Update governance rules by removing CODEOWNERS reference#30
damaz91 merged 1 commit into
mainfrom
chore/remove-codeowners

Conversation

@damaz91

@damaz91 damaz91 commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Description

Removed CODEOWNERS path from governance rules and excludes. We are switching governance enforcement to use a YAML based engine from https://github.com/Universal-Commerce-Protocol/.github/tree/main/org-tools/governance

We are currently testing the approach on the "python-sdk" repo. We'll roll back if we find any regression.

Category (Required)

Please select one or more categories that apply to this change.

  • Core Protocol: Changes to the base communication layer, global context, or breaking refactors. (Requires Technical Council approval)
  • Governance/Contributing: Updates to GOVERNANCE.md, CONTRIBUTING.md, or CODEOWNERS. (Requires Governance Council approval)
  • Capability: New schemas (Discovery, Cart, etc.) or extensions. (Requires Maintainer approval)
  • Documentation: Updates to README, or documentations regarding schema or capabilities. (Requires Maintainer approval)
  • Infrastructure: CI/CD, Linters, or build scripts. (Requires DevOps Maintainer approval)
  • Maintenance: Version bumps, lockfile updates, or minor bug fixes. (Requires DevOps Maintainer approval)
  • SDK: Language-specific SDK updates and releases. (Requires DevOps Maintainer approval)
  • Samples / Conformance: Maintaining samples and the conformance suite. (Requires Maintainer approval)
  • UCP Schema: Changes to the ucp-schema tool (resolver, linter, validator). (Requires Maintainer approval)
  • Community Health (.github): Updates to templates, workflows, or org-level configs. (Requires DevOps Maintainer approval)

Checklist

  • I have followed the Contributing Guide (including Conventional Commits title requirements and ! for breaking changes).
  • I have updated the documentation (if applicable).
  • My changes pass all local linting and formatting checks.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • (For Core/Capability) I have included/updated the relevant JSON schemas.
  • I have regenerated Python Pydantic models by running generate_models.sh under python_sdk.

Removed CODEOWNERS path from governance rules and excludes.
@damaz91 damaz91 requested a review from a team as a code owner June 24, 2026 11:12
@damaz91 damaz91 requested review from dwdii and wry-ry June 24, 2026 11:12

@ptiper ptiper left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please specify this is for testing and that the new system will apply enforcement if it works, we'll roll back if it doesn't

@damaz91 damaz91 merged commit f867851 into main Jun 24, 2026
9 checks passed
@damaz91 damaz91 deleted the chore/remove-codeowners branch June 24, 2026 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants